Performance data management device and business management system

ABSTRACT

A performance data processing section that receives performance data generated by a manufacturing site system; a performance data storage section that stores received performance data; a master data storage section that stores master data that has data to be basic information when the performance data is managed; a business data generation section that generates business data by processing the performance data into a structure used by a business application based on data to be the basic information in the master data; and a business data storage section that stores the business data are included, in which the master data includes an attribute that represents start of an effective period of data to be the basic information and an attribute that represents end of the effective period.

TECHNICAL FIELD

The present invention relates to a performance data management deviceand a business management system.

BACKGROUND ART

Business performance data is conventionally managed by a programprocessed on a computer for the purpose of streamlining and improvingbusiness. The above program is referred to as business application. At amanufacturing site, a certain business application operates on acomputerized information system to perform management information ofperformance data.

For example, PTL 1 discloses “finding a future production index value byperforming a production simulation on the basis of the performance data,and, in a case where the future production index value becomes lowerthan the current production index value, performing a productionsimulation by improvement master data corrected on the basis of possibleimprovement master data”.

CITATION LIST Patent Literature

-   PTL 1: JP 2017-174334 A

SUMMARY OF INVENTION Technical Problem

Performance data of a manufacturing site is used in many businessapplications. Therefore, there is a product that manages data of amanufacturing site and cooperates with a business application withoutperforming program modification. However, there is not a product thathas a function of maintaining consistency of a change in data, managesperformance data, and cooperates with a business application without aprogram.

In a case where a change occurs in the content of performance datamanaged by the business application, data inconsistency occurs unlessrelated data is changed with consistency maintained. For example, when aname of specific data is changed, data related to this specific datarefers to data after the change. In this case, for example, past dataregistered before the name change refers to the data after the namechange, and therefore data inconsistency occurs. At a manufacturingsite, since it is necessary to trace a trail from past performance data,a mechanism for changing data while ensuring consistency of past data isnecessary.

The present invention has been made in view of the above circumstances,and an object thereof is to ensure consistency of related data even whena change occurs in content of performance data of a manufacturing sitesystem.

Solution to Problem

In order to solve the above problem, a performance data managementdevice of one aspect of the present invention includes: a performancedata processing section that receives performance data generated by amanufacturing site system; a performance data storage section thatstores and accumulates the performance data received by the performancedata processing section; a master data storage section that storesmaster data that has data to be basic information when the performancedata is managed; a business data generation section that generatesbusiness data by processing the performance data into a structure usedby a business application based on data to be the basic information inthe master data; and a business data storage section that stores thebusiness data generated by the business data generation section. Themaster data includes an attribute that represents start of an effectiveperiod of data to be the basic information and an attribute thatrepresents end of the effective period.

A business management system of one aspect of the present inventionincludes: the performance data management device and a businessapplication that uses performance data managed by the performance datamanagement device.

Advantageous Effects of Invention

According to at least one aspect of the present invention, it ispossible to ensure consistency of related data even when a change occursin content of performance data of a manufacturing site system.

Problems, configurations, and effects other than those described abovewill be made clear by the description of the following embodiments.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a view illustrating an example of a manufacturing site system.

FIG. 2 is a block diagram illustrating an overall configuration exampleof a business management system in which the business applicationaccording to a first embodiment of the present invention usesperformance data of the manufacturing site system.

FIG. 3 is a block diagram illustrating a hardware configuration exampleof a computer included in each device constituting the manufacturingsite system and the business management system.

FIG. 4 is a view illustrating a configuration example of performancedata according to the first embodiment of the present invention.

FIG. 5 is a view illustrating a configuration example of master dataaccording to the first embodiment of the present invention.

FIG. 6 is a flowchart illustrating an operation example of a performancedata processing section according to the first embodiment of the presentinvention.

FIG. 7 is a flowchart illustrating an operation example of a master dataprocessing section according to the first embodiment of the presentinvention.

FIG. 8 is a view illustrating a configuration example of a performancedata storage section according to the first embodiment of the presentinvention.

FIG. 9 is a view illustrating a configuration example of a master datastorage section according to the first embodiment of the presentinvention.

FIG. 10 is a flowchart illustrating an operation example of a businessdata generation section according to the first embodiment of the presentinvention.

FIG. 11 is a view illustrating a configuration example of each table ofmaster data stored in the business data storage section according to thefirst embodiment of the present invention.

FIG. 12 is a view illustrating a configuration example of a table ofperformance data stored in the business data storage section accordingto the first embodiment of the present invention.

FIG. 13 is a block diagram illustrating a configuration example of amaster data registration section according to the first embodiment ofthe present invention.

FIG. 14 is a flowchart illustrating a procedure example of master dataregistration processing by the master data registration sectionaccording to the first embodiment of the present invention.

FIG. 15 is a view illustrating an example of a screen (item additionscreen) for registering item data according to the first embodiment ofthe present invention.

FIG. 16 is a view illustrating an example of an error screen output whenan invalid value is set in input information according to the firstembodiment of the present invention.

FIG. 17 is a flowchart illustrating a procedure example of master dataupdate processing by the master data registration section according tothe first embodiment of the present invention.

FIG. 18 is a view illustrating an example of a screen (item updatescreen) for updating item data according to the first embodiment of thepresent invention.

FIG. 19 is a view illustrating an example of a screen (bills ofmaterials definition screen) for registering BOM management informationaccording to the first embodiment of the present invention.

FIG. 20 is a view illustrating an example of a screen (bills ofmaterials definition screen) after registering BOM managementinformation according to the first embodiment of the present invention.

FIG. 21 is a view illustrating a change example of display content of ascreen (bills of materials definition screen) after registering BOMmanagement information due to a change in designated date and timeaccording to the first embodiment of the present invention.

FIG. 22 is a view illustrating an example of hierarchical structure dataof components registered for each effective period according to thefirst embodiment of the present invention.

FIG. 23 is a view illustrating an example of a screen (process additionscreen) for registering process data according to the first embodimentof the present invention.

FIG. 24 is a view illustrating an example of a screen (process additionscreen) for updating process data according to the first embodiment ofthe present invention.

FIG. 25 is a view illustrating an example of a screen (bills ofmaterials definition screen) for registering a process branch accordingto the first embodiment of the present invention.

FIG. 26 is a view illustrating an example of a screen (bills ofmaterials definition screen) after registering the process branchaccording to the first embodiment of the present invention.

FIG. 27 is a view illustrating a change example (bills of materialsdefinition screen) of display content of a screen after registering aprocess branch due to a change in designated date and time according tothe first embodiment of the present invention.

FIG. 28 is a view illustrating an example of screen display when thebusiness application according to the first embodiment of the presentinvention acquires data from the performance data management device.

FIG. 29 is a view illustrating a configuration example of performancedata classified into four elements of production according to a secondembodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

In general, business is repeatedly practiced, business performance dataincreases (accumulates) every day. This business data is used in variousbusiness applications. Therefore, there is a high demand for a method ofmanaging a large amount of business performance data and cooperating theperformance data with the business applications. For performance datamanagement at a manufacturing site, various methods have beenestablished. However, a performance data management method having amethod for ensuring consistency with respect to a change in theperformance data being managed has not been established.

For example, when a name of specific data is changed, related datarefers to data after the change. In this case, since past dataregistered before the name change refers to the data after the namechange, data inconsistency occurs. At a manufacturing site, since it isnecessary to trace a trail from past performance data, a mechanism forchanging data while ensuring consistency of past data is necessary.Therefore, the inventors have invented a management method that enablescooperation between management of performance data and a businessapplication and secures consistency of data.

First Embodiment

Examples of embodiments for carrying out the present invention will bedescribed below with reference to the accompanying drawings. In thepresent description and the accompanying drawings, constituent elementshaving substantially identical function or configuration are denoted byidentical reference signs, and redundant description is omitted. As thefirst embodiment of the present invention, a case where the presentinvention is applied to a business management system in whichperformance data of a manufacturing site system is used by a businessapplication will be described.

[Example of Work Site System]

First, an example of a manufacturing site system that generatesperformance data will be described with reference to FIG. 1 . FIG. 1illustrates an example of a manufacturing site system. A manufacturingsite system 1 (an example of a control system) illustrated in FIG. 1includes a processing machine 10 that performs preset processing on aprocessing target object to produce a processed product 20, and aplurality of machines such as an assembly machine and an inspectionmachine that are not illustrated. The manufacturing site system 1 isconnected with a controller not illustrated that controls themanufacturing site system 1 based on various state quantities, aproduction target, and the like acquired from the manufacturing sitesystem 1. In the processing machine 10, a housing that protects theprocessing machine is provided with an operation panel 11, a processingstart button 12, a processing end button 13, and a reader/writer device14.

The manufacturing site system 1 is connected with a terminal device 31and a performance data management device 200 via a field network N1. Theperformance data management device 200 is connected to a terminal device32 via a control network N2. The field network N1 and the controlnetwork N2 are wired or wireless local area networks (LAN). This networkconfiguration is an example, and for example, the controller may beconnected between the manufacturing site system 1 and the field networkN1.

A worker 40 sees work instructions R displayed on the terminal device 31or work content described in the printed matter of the work instructionsR to confirm that the processing work is instructed, and operates theprocessing machine 10. For example, before operating the processingmachine 10, the worker 40 holds an employee card 41 made of an IC cardover the reader/writer device 14 of the processing machine 10, andinputs worker information recorded on an IC chip of the employee card 41to the processing machine 10. Due to this, worker information (forexample, contact name) of the worker 40 who has operated the processingmachine 10 is recorded in the processing machine 10, that is, themanufacturing site system 1.

Thereafter, when the worker 40 presses the processing start button 12and the processing end button 13 based on the work instructions, theprocessing machine 10 executes processing start and processing end. Theprocessing machine 10 (manufacturing site system 1) outputs informationindicating operation performance to the performance data managementdevice 200 as performance data. The processing machine 10 (manufacturingsite system 1) creates performance data in a format that can beprocessed by the performance data management device 200.

Similarly, the worker 40 in charge of the work performs assembly work,inspection work, or other works based on the work instructions R.According to the work having been carried out, each performance data issequentially captured and managed in the performance data managementdevice 200. In the present embodiment, a series of works at amanufacturing site is referred to as “business”.

Note that the worker 40 may register the worker information of theworker 40 (and information on processing start by the worker 40) intothe performance data management device 200 by operating the operationpanel 11 or operating the terminal device 31. The processing machine 10may execute processing start and processing end by the worker 40inputting commands of processing start and processing end via theoperation panel 11.

For example, an operation procedure may be set such that a processingstart command to the processing machine 10 becomes possible by theoperator 40 operating the operation panel 11 or the terminal device 31to input worker information. In this case, the registration of theworker information (information on the processing start by the worker40) and the processing start of the processing machine 10 may beregistered in the performance data management device 200 at the sametime.

The processing machine 10 may include a code reader, and the worker 40may instruct processing start and processing end to the processingmachine 10 by operating the code reader to read information of a code(barcode, two-dimensional code, and the like) for each work printed(displayed) on the work instructions R.

[Overall Configuration of Business Management System]

Next, an overall configuration example of the business management systemwill be described with reference to FIG. 2 .

FIG. 2 is a block diagram illustrating an overall configuration exampleof a business management system 1000 in which the business applicationaccording to the first embodiment uses performance data of themanufacturing site system 1.

The business management system 1000 includes the performance datamanagement device 200 that acquires and manages performance data 110 andmaster data 120 from the manufacturing site system 1, a businessextract/transform/load (ETL) 710, a business data storage section 720,and a business application 730.

The manufacturing site system 1 generates and transmits, to theperformance data management device 200, the performance data 110including information indicating performance of the manufacturing sitesystem 1. The performance of the manufacturing site system 1 is a resultof operation, a produced product, a consumed substance, their amounts,and the like as a result of the dynamics and operation of themanufacturing site system 1.

(Performance Data Management Device)

The performance data management device 200 acquires and manages theperformance data 110 generated by the manufacturing site system 1. Theperformance data management device 200 creates business data from theperformance data 110 and provides the business data to the businessapplication 730. The performance data management device 200 acquires andmanages the master data 120 transmitted from the manufacturing sitesystem 1.

This performance data management device 200 includes a performance dataprocessing section 310, a performance data storage section 410, a masterdata processing section 320, a master data storage section 420, abusiness data generation section 500, a business data storage section600, and a master data registration section 210.

The performance data processing section 310 performs processing ofacquiring and recording, in the performance data storage section 410,the performance data 110 transmitted from the manufacturing site system1. The performance data 110 is data in which details of events that haveoccurred with actual business are recorded. The performance data issometimes referred to as transaction data.

The performance data storage section 410 is a nonvolatile or volatilestorage section in which the performance data 110 is recorded by theperformance data processing section 310.

The master data processing section 320 performs processing of acquiringand recording, in the master data storage section 420, the master data120 transmitted from the manufacturing site system 1. The master data120 is ledger data in which basic attribute information of items relatedto business is collected. In the present invention, transmission of themaster data 120 by the manufacturing site system 1 is not essential.

The master data storage section 420 is a nonvolatile or volatile storagesection in which the master data 120 is recorded by the master dataprocessing section 320.

The business data generation section 500 acquires performance datarecorded in the performance data storage section 410 and records theperformance data into performance data 610 in the business data storagesection 600. The business data generation section 500 updates theperformance data 610 in the business data storage section 600 with theacquired performance data. The business data generation section 500processes the acquired performance data into a structure (see an actualprocess table 611 in FIG. 12 , for example) that can be used by thebusiness application. The business data generation section 500 acquiresmaster data recorded in the master data storage section 420, and records(adds) the master data into master data 620 in the business data storagesection 600.

The business data storage section 600 is a nonvolatile or volatilestorage section in which the performance data 610 and the master data620 are recorded (accumulated) as data (business data) used by thebusiness application. The business data storage section 600 records themaster data 620 to be registered by the master data registration section210. As the master data 620, data necessary for management of theperformance data, such as an ID and a name of an item, and an ID and aname of a process, are managed.

The business data storage section 600 is also an example of aperformance data storage section and a master data storage section. Anarea in the business data storage section 600 where the performance data610 is recorded is sometimes referred to as “business data storagesection 600 (performance data)”. An area in the business data storagesection 600 where the master data 620 is recorded is sometimes referredto as “business data storage section 600 (master data)”.

On the basis of an instruction from a system manager 45, for example,the master data registration section 210 registers the master data 620into the business data storage section 600 or updates the master data620.

The business ETL 710 is a business data conversion processing sectionthat generates business data based on the performance data 610 and themaster data 620. The business ETL 710 extracts performance datacorresponding to a designated item ID, process ID, and the like from theperformance data 610 accumulated in the business data storage section600, and performs processing of converting the performance dataaccording to a purpose (business application 730). Then, the businessETL 710 stores the performance data subjected to the conversionprocessing, that is, the business data into the business data storagesection 720. Thus, when registering or updating the performance datainto the business data storage section 720, the business ETL 710registers the transaction data by using information of the master data620.

The business data storage section 720 is a nonvolatile or volatilestorage section that accumulates business data extracted from thebusiness data storage section 600 by the business ETL 710 and convertedaccording to the purpose.

The business application 730 is an application used for managing,streamlining, and improving business. Cooperating with the performancedata management device 200, the business application 730 outputs aresult by using business data stored in the business data storagesection 720. The user uses the business data in the performance datamanagement device 200 through the output result of the businessapplication 730.

Note that the business data generation section 500 and the business datastorage section 600 may be configured to function of both the businessETL 710 and the business data storage section 720.

[Hardware Configuration of Each Device]

FIG. 3 is a block diagram illustrating a hardware configuration exampleof a computer included in each device constituting the manufacturingsite system 1 and the business management system 1000. Each section inthe device is selected according to the function and purpose of use ofeach device. Here, a hardware configuration example of theabove-described performance data management device 200 will bedescribed.

A computer 50 of the performance data management device 200 includes acentral processing unit (CPU) 51, a read only memory (ROM) 52, a randomaccess memory (RAM) 53, a nonvolatile storage 57, and a communicationinterface 58. Sections in the performance data management device 200 areconnected to be able to transmit and receive data to and from oneanother via a system bus 54.

The CPU 51, the ROM 52, and the RAM 53 constitute a control section.This control section controls the operation of the entire performancedata management device 200 or each section. The CPU 51 reads, from theROM 52, and executes a program code of software for implementing eachfunction according to the present embodiment, and performs control ofeach section and various arithmetic operations. Instead of the CPU 51,another arithmetic processing unit such as a micro processing unit (MPU)may be used.

The ROM 52 is used as an example of a nonvolatile memory (recordingmedium), and the ROM 52 stores a program, data, and the like necessaryfor the CPU 51 to operate. The RAM 53 is used as an example of avolatile memory, and the RAM 53 temporarily stores a variable, aparameter, and the like generated in the middle of arithmetic processingby the CPU 51.

The nonvolatile storage 57 is an example of a recording medium, and canstore a program such as an operating system (OS), a parameter used whenthe program is executed, data obtained by executing the program, and thelike. For example, the performance data storage section 410, the masterdata storage section 420, and the business data storage section 600 inFIG. 2 are configured using the nonvolatile storage 57.

A program executed by the CPU 51 may be stored in the nonvolatilestorage 57. As the nonvolatile storage 57, a semiconductor memory, ahard disk, a solid state drive (SSD), a recording medium using magnetismor light, or the like is used. Note that the program may be provided viaa wired or wireless transmission medium such as a local area network(LAN), the Internet, or digital satellite broadcasting.

As the communication interface 58, for example, a network interface card(NIC), a modem, or the like is used, and is configured to be able totransmit and receive various data to and from an external device via anetwork such as a LAN to which a terminal is connected, a dedicatedline, or the like.

Note that the computer 50 may be provided with a display section 55 suchas a liquid crystal display and an operation section 56 such as a mouseand a keyboard. The display section 55 displays a GUI screen, a resultof processing performed by the CPU 51, and the like, and the operationsection 56 generates and supplies, to the CPU 51, an input signalaccording to a user's operation. For example, the worker 40, the systemmanager 45, and the like can check the screen displayed on the displaysection 55 and perform necessary editing through the operation section56.

The hardware configuration of the terminal devices 31 and 32 illustratedin FIG. 1 can also be configured similarly to the performance datamanagement device 200. A device mounted with at least the business ETL710 and/or the business application 730 can also have the hardwareconfiguration illustrated in FIG. 3 .

(Configuration of Performance Data)

FIG. 4 illustrates a configuration example of the performance data 110transmitted by the manufacturing site system 1.

As attributes (data items), the performance data 110 has, for example,an item ID 111, a process ID 112, a product ID 113, a data type 114, anevent type 115, and an event occurrence time 116.

The item ID 111 is information for uniquely identifying the item(information for uniquely identifying the type of the product).

The process ID 112 is information for uniquely identifying the process.

The product ID 113 is information for uniquely identifying the productof the corresponding item. These IDs are information for citing a nameregistered in the master data 620.

The data type 114 indicates the type (an event related to a machine, anevent related to a man, and the like) of data included in the presentdata.

The event type 115 indicates the event that has occurred. The eventsinclude start, end, middle, plan start, and plan end.

The event occurrence time 116 indicates the time at which an eventoccurs (start time, end time, and the like of a machine).

When these data are transmitted in a file format, the data type 114 orthe like may be transmitted as a file name.

(Configuration of Master Data)

FIG. 5 illustrates a configuration example of the master data 120transmitted by the manufacturing site system 1.

As attributes (data items), the master data 120 has, for example, a datatransmission time 121, an update/delete flag 122, a data type 123, datatype specific information 124, a vendor name 125, a data update date126, a data effective period start date 127, and a data effective periodend date 128.

The data transmission time 121 indicates the time at which the presentdata is transmitted.

The update/delete flag 122 is a flag indicating the type ofregistration, update, or deletion. Registration (addition), update, anddeletion of the present data to the master data 620 are determined onthe basis of the information of the update/delete flag 122.

The data type 123 indicates the type of the present data. The types ofdata include an item master and a process master.

The data type specific information 124 is specific information for eachmaster in the data type 123. An item name in the item master is anexample thereof.

The vendor name 125 indicates the name of the vendor. For example, thevendor is a company that manufactures (or delivers) a product, acomponent, a material, or the like, a company that executes a process,and the like.

The data update date 126 indicates the date when the present data isupdated in a case where the update/delete flag 122 indicates update.

The data effective period start date 127 indicates the start date of theeffective period of the present data.

The data effective period end date 128 indicates the end date of theeffective period of the present data.

In a case where these data are transmitted in a file format, the datatype 123 or the like may be transmitted as a file name.

[Operation of Performance Data Processing Section]

Next, the operation of the performance data processing section 310 willbe described with reference to FIG. 6 .

FIG. 6 is a flowchart illustrating an operation example of theperformance data processing section 310.

First, the performance data processing section 310 determines whetherthe performance data 110 has been received from the manufacturing sitesystem 1 (S1), and ends the processing of the present flowchart if theperformance data 110 has not been received (NO in S1).

Next, if the performance data 110 has been received (YES in S1), theperformance data processing section 310 determines whether an invalidvalue has been set in the performance data 110 (S2), and ends theprocessing of the present flowchart if an invalid value has been set(YES in S2). For example, in a case where the start time and the endtime of the performance data are reversed in time series, it is regardedas an invalid value. In a case where the event occurrence time is aheadof the current time point, it corresponds to an invalid value.

Next, if an invalid value has not been set (NO in S2), the performancedata processing section 310 registers the performance data 110 into theperformance data storage section 410 (S3), and ends the processing ofthe present flowchart.

[Master Data Processing Section]

Next, the operation of the master data processing section 320 will bedescribed with reference to FIG. 7 .

FIG. 7 is a flowchart illustrating an operation example of the masterdata processing section 320.

First, the master data processing section 320 determines whether themaster data 120 has been received from the manufacturing site system 1(S11), and ends the processing of the present flowchart if the masterdata 120 has not been received (NO in S11).

Next, if the master data 120 has been received (YES in S11), the masterdata processing section 320 determines whether an invalid value has beenset in the master data 120 (S12), and ends the processing of the presentflowchart if an invalid value has been set (YES in S12). For example, ina case where the event occurrence time is ahead of the current timepoint, it corresponds to an invalid value.

Next, if an invalid value has not been set (NO in S12), the master dataprocessing section 320 registers the master data 120 into the masterdata storage section 420 (S13), and ends the processing of the presentflowchart.

[Configuration of Performance Data Storage Section]

FIG. 8 illustrates a configuration example of the performance datastorage section 410.

The performance data storage section 410 has a field of the sameattribute (data item) as that of the performance data 110 (FIG. 4 ).That is, the performance data storage section 410 includes fields of theitem ID 111, the process ID 112, the product ID 113, the data type 114,the event type 115, and the event occurrence time 116.

For example, in FIG. 8 , each piece of information of the item ID 111“1”, the process ID 112 “010”, the product ID 113 “1234567”, the datatype 114 “MACHINE 001”, the event type 115 “START”, and the eventoccurrence time 116 “2019/12/01 10:00:00” is registered in the firstrecord of the performance data storage section 410.

[Configuration of Master Data Storage Section]

FIG. 9 illustrates a configuration example of the master data storagesection 420.

The master data storage section 420 has a field of the same attribute(data item) as that of the master data 120 (FIG. 4 ). That is, themaster data storage section 420 has each field of the data transmissiontime 121, the update/delete flag 122, the data type 123, the data typespecific information 124, the vendor name 125, the data update date 126,the data effective period start date 127, and the data effective periodend date 128. In each data (record), the start date and the end date ofthe data effective period are set.

For example, in FIG. 9 , each piece of information of the datatransmission time 121 “2019/11/01 10:00:00”, the update/delete flag 122“REGISTRATION”, the data type 123 “ITEM MASTER”, the data type specificinformation 124 “TELEVISION A”, the vendor name 125 “VENDOR A”, the dataupdate date 126 “2019/12/01 00:00:00”, the data effective period startdate 127 “2019/11/01 10:00:00”, and the data effective period end date128 “2020/11/30 23:59:59” is registered in the first record of themaster data storage section 420.

Each data in the performance data storage section 410 and the masterdata storage section 420 can be configured using comma-separated values(CSV) as an example.

[Operation of Business Data Generation Section]

Next, the operation of the business data generation section 500 will bedescribed with reference to FIG. 10 .

FIG. 10 is a flowchart illustrating an operation example of the businessdata generation section 500. The business data generation section 500executes the processing of the present flowchart at a predeterminedcycle.

First, the business data generation section 500 determines whether datastored in the master data storage section 420 has been updated(registration and change of data). For example, whether the data in themaster data storage section 420 has been updated can be determined bydetecting an increase in recorded data (record), an increase in filesize, or the like. Then, if the data in the master data storage section420 has not been updated (NO in S21), the business data generationsection 500 moves to step S22.

Next, the business data generation section 500 determines whether datastored in the performance data storage section 410 has been updated(registration and change of data) (S22). If the data in the performancedata storage section 410 has been updated (YES in S22), the businessdata generation section 500 determines whether reference data (dataitem) of the corresponding performance data exists in the business datastorage section 600 (master data) (S23). Here, if the reference data(data item) exists in the business data storage section 600 (masterdata) (YES in S23), the business data generation section 500 registersthe corresponding performance data into the business data storagesection (performance data) (S24). After the processing of step S24, thebusiness data generation section 500 ends the processing of the presentflowchart.

If the data in the performance data storage section 410 has not beenupdated (NO in S22) or if the reference data (data item) of thecorresponding performance data does not exist in the business datastorage section 600 (master data) (NO in S23), the business datageneration section 500 ends the processing of the present flowchart.Unless the reference data exists in the business data storage section600 (master data), the performance data subject to update cannot bemanaged as business data.

Next, if the data in the master data storage section 420 has beenupdated (YES in S21), the business data generation section 500determines whether the effective period of the updated data is valid(S25). For example, in a case where the effective period start date andthe effective period end date are reversed in time series, the effectiveperiod is not valid. If the effective period of the updated data is notvalid (NO in S25), the business data generation section 500 ends theprocessing of the present flowchart.

Next, if the effective period is valid (YES in S25), the business datageneration section 500 determines whether a parent ID exists in the dataitem of the updated data (S26). The parent ID has a parent-childrelationship between data in a BOM master table, a sequence mastertable, and the like. Then, the business data generation section 500moves to step S27 if the parent ID exists (YES in S26), and ends theprocessing of the present flowchart if the parent ID does not exist (NOin S26).

Next, the business data generation section 500 confirms theupdate/delete flag 122 (see FIG. 9 ) of the corresponding master dataand determines whether master data registration processing is necessary(S27). If the registration flag is on in the update/delete flag 122, itis necessary to register the corresponding master data into the businessdata storage section 600. Here, the business data generation section 500moves to step S28 if performing the master data registration processing(YES in S27), and moves to step S30 if not performing the master dataregistration processing (NO in S27).

Next, the business data generation section 500 determines whether masterdata having an effective period overlapping with that of the updatedmaster data in the master data storage section 420 exists in thebusiness data storage section 600 (master data) (S28). Next, if theeffective period of the master data does not overlap (NO in S28), thebusiness data generation section 500 registers the updated master datainto the business data storage section 600 (master data) (S29). Afterthe processing of step S29 or if the effective period of the master dataoverlaps (YES in S28), the business data generation section 500 ends theprocessing of the present flowchart.

On the other hand, if not performing the master data registrationprocessing (NO in S27), the business data generation section 500confirms the update/delete flag 122 and determines whether the masterdata subject to update exists (the update flag is on) (S30). If themaster data subject to update exists (YES in S30), the business datageneration section 500 determines whether master data having aneffective period overlapping with that of the updated master data in themaster data storage section 420 exists in the business data storagesection 600 (master data) (S31). Next, if master data having anoverlapping effective period does not exist (NO in S31), the businessdata generation section 500 records (updates) the updated master datainto the business data storage section 600 (master data) (S32).

After the processing of step S31, the processing of the presentflowchart is ended. If the master data subject to update does not exist(NO in S30) or if master data having an overlapping effective periodexists (YES in S31), the business data generation section 500 ends theprocessing of the present flowchart.

[Table Configuration of Master Data]

FIG. 11 illustrates a configuration example of each table of the masterdata 620 stored in the business data storage section 600.

As examples of the master data 620, an item master table 621, a processmaster table 622, a BOM master table 623, and a sequence master table624 are presented in the business data storage section 600.

(Item Master Table)

The item master table 621 is a table indicating a correspondencerelationship between the item ID and the item name, and has “ITEM ID”,“ITEM NAME”, “EFFECTIVE PERIOD START DATE”, and “EFFECTIVE PERIOD ENDDATE” as fields.

The item ID is the same as the item ID 111 (FIGS. 4 and 8 ), and isinformation for uniquely identifying the item.

The item name indicates the name of the item specified by the item ID.

The effective period start date indicates the start date of theeffective period of the present data (record).

The effective period end date indicates the end date of the effectiveperiod of the present data (record).

In the example of FIG. 11 , “TELEVISION A” and “TELEVISION B” areregistered as the item name for the item ID “1”. As illustrated in FIG.9 , the television A is manufactured by the vendor A, and the televisionB is manufactured by a vendor B. After the effective period of the datafor the television A ends, the effective period of the data for thetelevision B subsequently starts.

(Process Master Table)

The process master table 622 is a table indicating a correspondencerelationship between the process ID and the process name, and has“PROCESS ID”, “PROCESS NAME”, “EFFECTIVE PERIOD START DATE”, and“EFFECTIVE PERIOD END DATE” as fields.

The process ID is the same as the process ID 112 (FIGS. 4 and 8), and isinformation for uniquely identifying the process.

The process name indicates the name of the process specified by theprocess ID.

The effective period start date indicates the start date of theeffective period of the present data (record).

The effective period end date indicates the end date of the effectiveperiod of the present data (record).

In the example of FIG. 11 , “painting” and “PAINTING” are registered asthe process name for the process ID “10”. This is because the manager 45has input one process name in lower case and the other process name inupper case when registering the process name. For example, also in acase of using other scripts or other symbols, there is a possibledifference in half-width/full-width, upper-case/lower-case, and thelike. After the effective period of the data for “painting” ends, theeffective period of the data for “PAINTING” subsequently starts.

(BOM Master Table)

The BOM master table 623 is a table indicating a correspondencerelationship among the parent item ID, the child item ID, and thenumber, and has “PARENT ITEM ID”, “CHILD ITEM ID”, “NUMBER”, “EFFECTIVEPERIOD START DATE”, and “EFFECTIVE PERIOD END DATE” as fields.

The parent item ID indicates a parent item among items in a parent-childrelationship, and corresponds to the item ID of the item master table.

The child item ID indicates a child item among items in the parent-childrelationship.

The number indicates the quantity of child items.

The effective period start date indicates the start date of theeffective period of the present data (record).

The effective period end date indicates the end date of the effectiveperiod of the present data (record).

(Sequence Master Table)

The sequence master table 624 is a table indicating a correspondencerelationship between the parent process ID and the child process ID, andhas “PARENT PROCESS ID”, “CHILD PROCESS ID”, “EFFECTIVE PERIOD STARTDATE”, and “EFFECTIVE PERIOD END DATE” as fields.

The parent process ID indicates a parent process (upstream process)among processes in a parent-child relationship, and corresponds to theprocess ID in the process master table.

The child process ID indicates a child process among processes in theparent-child relationship.

The effective period start date indicates the start date of theeffective period of the present data (record).

The effective period end date indicates the end date of the effectiveperiod of the present data (record).

In the master table described above, the effective period sometimeschanges when the data is changed. For example, in a case where the itemname is changed in the item master table 621, the effective period ischanged while the item ID remains the same, and the item name after thechange is registered. Therefore, consistency of related data is ensuredby the attribute of this effective period even if the content of theperformance data is changed.

[Table Configuration of Performance Data (Actual Process Table)]

FIG. 12 illustrates a configuration example of the table of theperformance data 610 stored in the business data storage section 600.

In the business data storage section 600, the actual process table 611is illustrated as an example of the performance data 610. The actualprocess table 611 includes “ACTUAL PROCESS ID”, “ITEM ID”, “PROCESS ID”,“PERFORMANCE START TIME”, and “PERFORMANCE END TIME”.

The actual process ID is identification information for processmanagement, and IDs are given in time series, for example. The item IDis the same as the item ID 111 (FIGS. 4 and 8 ), and is information foruniquely identifying the item.

The process ID is the same as the process ID 112 (FIGS. 4 and 8 ), andis information for uniquely identifying the process.

The performance start time is a time indicated by the event occurrencetime 116 when the event type 115 (FIGS. 4 and 8 ) is “START”.

The performance end time is a time indicated by the event occurrencetime 116 when the event type 115 (FIGS. 4 and 8 ) is “END”.

As described above, the business data storage section 600 manages themaster data 620 by the effective period. Therefore, the process name andthe item name to be acquired from the master data 620 by the businessdata generation section 500 vary depending on the performance start timeand the performance end time of the process.

[Master Data Registration Section]

Next, the master data registration section 210 will be described indetail.

FIG. 13 is a block diagram illustrating a configuration example of themaster data registration section 210. FIG. 13 will be described assumingthat the performance data management device 200 includes the displaysection 55 and the operation section 56.

The master data registration section 210 includes a master data displaycontrol section 211, a master definition edit section 212, and a masterdata registration screen processing section 213. The master data displaycontrol section 211 and the master definition edit section 212correspond to a server (application software). The master dataregistration screen processing section 213 corresponds to a browser(application software).

The master data display control section 211 reads the master data 620from the business data storage section 600 (master data), and outputs afile of the master data 620 to the master data registration screenprocessing section 213 together with a file such as a registrationscreen or an update screen.

On the basis of the master data 620 input from the master data displaycontrol section 211 and the files of various screens, the master dataregistration screen processing section 213 constitutes the variousscreens and displays the master data on the display section 55. Themaster data registration screen processing section 213 outputs, to themaster definition edit section 212, an editing instruction for themaster data 620 performed through the operation section 56 by themanager 45 or the like who saw the various screens.

The master definition edit section 212 edits and stores, into thebusiness data storage section 600 (master data), the master data 620 onthe basis of the editing instruction input from the master dataregistration screen processing section 213.

[Master Data Registration Processing]

Next, the master data registration processing will be described withreference to FIG. 14 .

FIG. 14 is a flowchart illustrating a procedure example of the masterdata registration processing by the master data registration section210.

First, when the manager 45 selects a menu for registering (adding)master data from a menu screen (not illustrated) with the operationsection 56, the master data registration section 210 receives aninstruction of this selection. The master data registration screenprocessing section 213 displays, on the display section 55, a screen forregistering (adding) the master data (for example, an item additionscreen 220 illustrated in FIG. 15 ).

Then, when the manager 45 inputs, on the item addition screen 220, theinformation of the master data desired to register by the operationsection 56, the information of the master data to be registered is inputto the master data registration screen processing section 213 (S41).Thereafter, the master data registration screen processing section 213receives a registration instruction by pressing a registration button(see FIG. 15 ) and instructs the master definition edit section 212 forregistration processing. Next, the master definition edit section 212determines whether an invalid value has been set in the input masterdata information (S42). Here, if determining that an invalid value hasnot been set in the input information (NO in S42), the master definitionedit section 212 stores the input master data information (item data)into the master data 620 in the business data storage section 600 (S43).

In the present embodiment, when the master data is registered using theitem addition screen 220, the master definition edit section 212automatically gives and registers, into the master data 620, an item IDon the basis of the item name and/or item description. However, an itemID field may be provided so as to allow the manager 45 to directly inputthe item ID with the operation section 56. Note that the initial valueof the version of the newly registered master data is “1”. The versionis information for distinguishing between new and old master data, andin the present embodiment, the larger the value is, the newer the masterdata is.

On the other hand, if determining that an invalid value has been set inthe input information (YES in S42), the master definition edit section212 invalidates the input information and notifies the master datadisplay control section 211 of an error. Upon receiving the errornotification, the master data display control section 211 outputs anerror screen 225 (see FIG. 16 ) described later to the display section55 (S44). After the processing of step S43 or S44, the processing of thepresent flowchart is ended.

[Item Addition Screen]

Next, a screen for registering item data (item addition screen) will bedescribed with reference to FIG. 15 .

FIG. 15 illustrates an example of a screen for registering item data(the item addition screen 220).

The item addition screen 220 includes an item name field 221 and aneffective period field 222. In addition, the item addition screen 220includes at least an item description field, a part number field, afigure number field, an item group field, a registration button, and acancel button. A feature of the item addition screen 220 is to includethe effective period field 222. A well-known technique can be used forother configurations of the item addition screen 220.

The item name field 221 is a field for inputting the name of an item tobe added.

The effective period field 222 is a field for inputting the effectiveperiod of the master data (record) registered on the item additionscreen 220.

The item description field is a field for inputting the description ofan item (product) indicated by an item name. The part number field is afield for inputting a number (a numeral or a symbol such as Romanalphabet) for identifying the type of the item (product) indicated bythe item name.

The figure number is a field for inputting the number of a designdrawing (mostly CAD data in general) of the item to be specified by thepart number.

The item group is a field for inputting a group into which the item(product) indicated by the item name is classified.

The registration button is a button for registering the inputinformation into the master data 620.

The cancel button is a button for canceling registration of the inputinformation into the master data 620.

FIG. 16 illustrates an example of an error screen to be output when aninvalid value is set in the input information. As explained in step S44of FIG. 14 , the master definition edit section 212 outputs the errorscreen 225 when an invalid value is set in the input information. Forexample, in a case where the effective period start date and theeffective period end date in the effective period field 222 are reversedin time series, an error occurs. At this time, a message “UNABLE TOREGISTER INPUT DATA BECAUSE EFFECTIVE PERIOD IS IMPROPER” is displayedon the error screen 225.

[Master Data Update Processing]

Next, the master data update processing will be described with referenceto FIG. 17 .

FIG. 17 is a flowchart illustrating a procedure example of the masterdata update processing by the master data registration section 210.

First, when the manager 45 selects a menu for updating (changing) masterdata from a menu screen (not illustrated) with the operation section 56,the master data registration section 210 receives an instruction of thisselection. The master data registration screen processing section 213displays, on the display section 55, a screen for updating (changing)the master data. When the manager 45 designates master data desired toupdate by the operation section 56, a screen (for example, an itemupdate screen 230 illustrated in FIG. 18 ) for updating the designatedmaster data is displayed on the display section 55.

Then, when the manager 45 inputs, on the item update screen 230, theinformation of the master data desired to update by the operationsection 56, the information of the master data to be updated is input tothe master data registration screen processing section 213 (S51).Thereafter, the master data registration screen processing section 213receives an update instruction by pressing an update button (see FIG. 18) and instructs the master definition edit section 212 for updateprocessing.

Next, the master definition edit section 212 determines whether additionof master data of a new version has been instructed (S52). Here, ifaddition of master data of the new version has not been instructed (NOin S52), the master definition edit section 212 moves to step S53. Then,the master definition edit section 212 determines whether the effectiveperiod of the master data (designated record) to which updateinformation is input overlaps the effective period of master data(another record) of another version (S53). The version of master datawill be described in detail with reference to FIG. 18 .

Next, if the effective period of the master data to which updateinformation is input overlaps the effective period of master data ofanother version (YES in S53), the master definition edit section 212invalidates the input information and ends the processing of the presentflowchart. Note that, in a case where there is only one version,determination is not performed regarding overlap of the effectiveperiod. However, similarly to step S42, it is determined whether or notan invalid value has been set in the input information. If an invalidvalue has been set in the input information, it is desirable toinvalidate the input information and output an error. Also if there isan overlap in the effective period, it is preferable to output an error.

Next, if the effective period of the master data to which updateinformation is input does not overlap the effective period of masterdata of another version (NO in S53), the master definition edit section212 updates the master data 620 in the business data storage section 600(S54).

On the other hand, if addition of master data of the new version hasbeen instructed (YES in S52), the master definition edit section 212moves to step S55. Then, the master definition edit section 212determines whether the effective period of the master data (new record)of the new version overlaps the effective period of master data (anotherrecord) of an existing version (S55).

Next, if the effective period of the master data of the new versionoverlaps the effective period of the master data of an existing version(YES in S55), the master definition edit section 212 invalidates theinput information and ends the processing of the present flowchart.

Next, if the effective period of the master data of the new version doesnot overlap the effective period of the master data of an existingversion (NO in S55), the master definition edit section 212 storesinformation of the master data of the new version into the master data620 in the business data storage section 600 (S56). After the processingof step S54 or S56, the processing of the present flowchart is ended.

[Item Update Screen]

Next, a screen (item update screen) for updating item data will bedescribed with reference to FIG. 18 .

FIG. 18 illustrates an example of a screen (item update screen 230) forupdating item data.

The item update screen 230 includes at least an item ID field 233 and aversion field 234 in addition to the configuration of the item additionscreen 220. The item update screen 230 includes an update button insteadof a registration button. A feature of the item update screen 230 is toinclude an effective period field 232 and the version field 234.

An item name field 231 is the same as the item name field 221.

The effective period field 232 is a field for inputting the effectiveperiod of the master data (record) updated on the item update screen230.

The item ID field 233 is a field for inputting information correspondingto the item ID field of the item master table 621 illustrated in FIG. 11. In the item master table 621, the item ID “1” indicates “TELEVISION”.In the present embodiment, the item addition screen 220 does not displaythe item ID, but the item update screen 230 displays the item ID.

The version field 234 is a field for inputting the version of thepresent data (record). It is possible to increase the version of data byoperating the version field 234. As the version field 234, for example,a graphical user interface (GUI) such as a pull-down menu or a list boxcan be used.

In the item update screen 230 of FIG. 18 , “VERSION 2” is displayed inthe version field 234. When the version of the designated master tableis changed from “1” to “2”, the master table of the version 2 is newlycreated while leaving the master table of the old version 1. On the itemupdate screen 230, the item name is changed to “TELEVISION B” withrespect to the master table (version 1) registered on the item additionscreen 220, and the effective period is set to “2019/01/01 TO2024/12/31” in order to avoid overlap with the version 1. Then, byselecting the version 2 in the version field 234 and pressing the updatebutton, the master table of the version 2 is created with this content.

[Bills of Materials Definition Screen (Item) Before Registration]

Next, a screen (bills of materials definition screen) for registeringBOM management information will be described with reference to FIG. 19 .In business management, a parts list is also referred to as bills ofmaterials (BOM).

FIG. 19 illustrates an example of a screen (bills of materialsdefinition screen 240) for registering BOM management information.

The bills of materials definition screen 240 has a BOM managementinformation area 241 in the upper part of the screen and a componenthierarchical structure area 248 indicating components constituting anitem (product) in the lower part of the screen.

The BOM management information area 241 is an area for displayinginformation for managing components and materials necessary for assemblyof an item (product).

The component hierarchical structure area 248 is an area for displayinga hierarchical structure of components.

The BOM management information area 241 includes an item ID field 242,an item name field 243, a version field 244, an effective period field245, a parent-child item start point field 246 (parent item), and aparent-child item end point field 247 (child item). In addition, the BOMmanagement information area 241 includes a hierarchy field, a numberfield, an inventory field, an add button, an update button, and a deletebutton.

The item ID field 242 is a field into which information of “PARENT ITEMID+CHILD ITEM ID” of the BOM master table 623 illustrated in FIG. 11 isinput.

The item name field 243 is a field for inputting the name of an item(component) subjected to definition.

The version field 244 is a field for inputting the version of thepresent data (record).

The effective period field 245 is a field for inputting the effectiveperiod of the master data (record) defined on the bills of materialsdefinition screen 240.

The parent-child item start point field 246 (parent item) is a field forinputting the item name of a parent item among items in a parent-childrelationship.

The parent-child item end point field 247 (child item) is a field forinputting the item name of a child item among items in a parent-childrelationship.

The hierarchy field is a field for inputting the number of hierarchiesof components of an item (television A in this example) specified by theitem ID.

The number field is a field for inputting the quantity of the itemsindicated by the item name.

The inventory field is a field for inputting the inventory of the itemsindicated by the item name.

The add button is a button for adding (registering) the inputinformation to the master data 620.

The update button is a button for updating the master data 620 with theinput information.

The delete button is a button for canceling registration of the inputinformation into the master data 620.

An item ID field, a date and time designation field 249, and a displaybutton are provided above the component hierarchical structure area 248.

The item ID field is a field for inputting information corresponding tothe item ID field of the item master table 621 illustrated in FIG. 11 .

The date and time designation field 249 is a field for inputting thedate and time desired to designate. When the date and time isdesignated, the hierarchical structure of the components at thedesignated date and time is displayed in the component hierarchicalstructure area 248. That is, the hierarchical structure of thecomponents to be displayed changes depending on the designated date andtime.

The display button is a button for displaying the hierarchical structureof components. When the display button is pressed after the date andtime is designated, the hierarchical structure of the components definedat the time point of the designated date and time is displayed.

A feature of the bills of materials definition screen 240 is to includethe effective period field 245, the version field 244, and the date andtime designation field 249.

On the bills of materials definition screen 240 illustrated in FIG. 19 ,components constituting the television A are displayed in a 3-layerhierarchical structure in the component hierarchical structure area 248.“LIQUID CRYSTAL PANEL”, “SUBSTRATE”, and “COVER” are connected to alayer (second layer) below “TELEVISION A” (first layer), and “GLASS” isconnected to a layer (third layer) below “LIQUID CRYSTAL PANEL”. In thefigure, “×n” (n is a natural number) on the right side of the componentindicates the number of components.

[Bills of Materials Definition Screen (Item) after Registration]

FIG. 20 illustrates an example of a screen (bills of materialsdefinition screen 280) after registration of BOM management information.

When the add button is pressed in a state where the BOM managementinformation illustrated in FIG. 19 is input onto the bills of materialsdefinition screen 240, the content changes to the content of the billsof materials definition screen 240 illustrated in FIG. 20 . Here, in thecomponent hierarchical structure area 248, one “LIQUID CRYSTAL” isconnected to the layer below “LIQUID CRYSTAL PANEL” in addition to“GLASS”.

This allows the manager 45 to confirm that “LIQUID CRYSTAL” has beenadded to the hierarchical structure of the components of the televisionA in the component hierarchical structure area 248 of the bills ofmaterials definition screen 240.

[Bills of Materials Definition Screen (Item) after Designated Date andTime is Changed]

Next, a change in the display content of the screen after registrationof the BOM management information due to the change of the designateddate and time will be described with reference to FIG. 21 .

FIG. 21 illustrates a change example of the display content of thescreen (bills of materials definition screen) after registering BOMmanagement information due to a change in designated date and time.

In the date and time designation field 249, the date and time to bedesignated is changed from “2017/01/01” to “2020/01/01”, and the displaybutton is pressed. Due to this, the hierarchical structure of componentsassociated with an effective period including “2020/01/01” is displayed.For example, in FIG. 21 , the item is changed from “TELEVISION A” to“TELEVISION B” and the components of the television B are indicated in a3-layer hierarchical structure. “LIQUID CRYSTAL PANEL”, “CENTERSUBSTRATE”, and “COVER” are connected to a layer (second layer) below“TELEVISION B” (first layer), “GLASS” and “LIQUID CRYSTAL” are connectedto a layer (third layer) below “LIQUID CRYSTAL PANEL”, and “SUBSTRATE(1)” and “SUBSTRATE (2)” are connected to a layer (third layer) below“CENTER SUBSTRATE”.

FIG. 22 illustrates an example of hierarchical structure data ofcomponents registered for each effective period.

The upper part of FIG. 22 illustrates hierarchical structure data 251 ofthe components with the effective period in 2015/01/01 to 2018/12/31.The lower part of FIG. 22 illustrates hierarchical structure data 252 ofthe components with the effective period in 2019/01/01 to 2024/12/31.Between the two effective periods, the item is changed from “TELEVISIONA” to “TELEVISION B”, and “TELEVISION B” has an increased number ofcomponents than “TELEVISION A”. The hierarchical structure data of thecomponents for each effective period is stored in the nonvolatilestorage 57.

Thus, in the present embodiment, by having a function of setting aneffective period to the master data and designating a date and time inthe date and time designation field 249, it is possible to confirm thehierarchical structure of components at the designated date and time.

[Process Addition Screen]

Next, a screen (process addition screen) for registering process datawill be described with reference to FIG. 23 .

FIG. 23 illustrates an example of a screen (process addition screen 260)for registering process data.

The process addition screen 260 includes a process name field 261 and aneffective period field 262. In addition, the process addition screen 260includes at least a process description field, a standard time (ST)field, a registration button, and a cancel button. The mostcharacteristic feature of the process addition screen 260 is to includean effective period field 262.

The process name field 261 is a field for inputting the name of aprocess to be added.

The effective period field 262 is a field for inputting the effectiveperiod of the master data (record) to be registered on the processaddition screen 260.

The process description field is a field for inputting the descriptionof a process indicated by the process name.

The ST field is a field for inputting work time required to complete atarget process.

By executing the flowchart of FIG. 14 using the process addition screen260, the master data registration section 210 stores the input masterdata information (process data) into the master data 620 in the businessdata storage section 600.

[Process Update Screen]

Next, a screen (process update screen) for updating process data will bedescribed with reference to FIG. 24 .

FIG. 24 illustrates an example of a screen (process update screen 270)for updating process data.

The process update screen 270 includes at least a process ID field 273and a version field 274 in addition to the configuration of the processaddition screen 260. The process update screen 270 includes an updatebutton instead of a registration button. A feature of the process updatescreen 270 is to include a version field 274 and an effective periodfield 272.

A process name field 271 is the same as the process name field 261.

The effective period field 272 is a field for inputting the effectiveperiod of the master data (record) updated on the process update screen270.

The process ID field 273 is a field for inputting informationcorresponding to the process ID field of the process master table 622illustrated in FIG. 11 . In the process master table 622, the process ID“10” indicates “painting” or “PAINTING”. In the present embodiment, theprocess addition screen 260 does not display the process ID, but theprocess update screen 270 displays the process ID.

The version field 274 is a field for inputting the version of thepresent data (record).

By executing the flowchart of FIG. 17 using the process update screen270, the master data registration section 210 updates the master data620 in the business data storage section 600 with the input master datainformation (process data).

[Bills of Materials Definition Screen (Process) Before Registration]

Next, a screen (bills of materials definition screen) for registering aprocess branch will be described with reference to FIG. 25 .

FIG. 25 illustrates an example of a screen (bills of materialsdefinition screen 280) for registering a process branch.

The bills of materials definition screen 280 has a process managementinformation area 281 in the upper part of the screen and a processhierarchical structure area 288 indicating a process procedure in thelower part of the screen.

The process management information area 281 is an area for displayinginformation for managing a process of manufacturing an item (product).

The process hierarchical structure area 288 is an area for displayingthe hierarchical structure of the process.

The process management information area 281 includes a process ID field282, a process name field 283, a version field 284, an effective periodfield 285, an upstream-side parent-child process field 286, and adownstream-side parent-child process field 287. In addition, the processmanagement information area 281 includes a hierarchy field, an addbutton, an update button, and a delete button.

The process ID field 282 is a field into which information of “PARENTPROCESS ID+CHILD PROCESS ID” of the sequence master table 624illustrated in FIG. 11 is input.

The process name field 283 is a field for inputting the name of aprocess subjected to definition.

The version field 284 is a field for inputting the version of thepresent data (record).

The effective period field 285 is a field for inputting the effectiveperiod of the master data (record) defined on the bills of materialsdefinition screen 280.

The upstream-side parent-child process field 286 is a field forinputting the process names of a start point and an end point of anupstream-side path among the paths constituting the branch process. Theprocess name of this start point is the name of a process specified bythe parent process ID of the sequence master table 624 (FIG. 11 ), andthe process name of the end point is the name of a process specified bythe child process ID of the sequence master table 624.

The downstream-side parent-child process field 287 is a field forinputting the process names of a start point and an end point of adownstream-side path among the paths constituting the branch process.The process name of this start point is the name of a process specifiedby the parent process ID of the sequence master table 624 (FIG. 11 ),and the process name of the end point is the name of a process specifiedby the child process ID of the sequence master table 624.

The hierarchy field is a field for inputting the number of hierarchiesof the processes specified by the process ID 282.

An item ID field, a date and time designation field 289, and a displaybutton are provided above the process hierarchical structure area 288.

The item ID field is a field for inputting information corresponding tothe item ID field of the item master table 621 illustrated in FIG. 11 .

The date and time designation field 289 is a field for inputting thedate and time desired to designate. When the date and time isdesignated, the hierarchical structure of the processes at thedesignated date and time is displayed in the process hierarchicalstructure area 288. That is, the hierarchical structure of the processesto be displayed changes depending on the designated date and time.

The display button is a button for displaying the hierarchical structureof processes. When the display button is pressed after the date and timeis designated, the hierarchical structure of the processes defined atthe time point of the designated date and time is displayed.

On the bills of materials definition screen 280 illustrated in FIG. 25 ,the process hierarchical structure area 288 displays a 3-layerhierarchical structure as processes indicated by the upstream-sideparent-child process field 286 and the downstream-side parent-childprocess field 287. That is, “SORTING” is set in a downstream process(second layer) of “CABLE PRODUCTION” (first layer), and “UNIT ASSEMBLY”is set in a downstream process (third layer) of “SORTING”.

[Bills of Materials Definition Screen (Process) after Registration]

FIG. 26 illustrates an example of a screen (bills of materialsdefinition screen 280) after registering the process branch.

When the add button is pressed in a state where the process managementinformation illustrated in FIG. 25 is input onto the bills of materialsdefinition screen 280, the content changes to the content of the billsof materials definition screen 280 illustrated in FIG. 26 . Here, theprocess hierarchical structure area 288 displays a state of branchinginto “SORTING” and “ELECTRIC WIRE FABRICATION” as a downstream processof “CABLE PRODUCTION”. Then, after “SORTING” and “ELECTRIC WIREFABRICATION”, the process merges with the process of “UNIT ASSEMBLY”.

This allows the manager 45 to confirm that the process of “ELECTRIC WIREFABRICATION” is branched separately from “SORTING” between “CABLEPRODUCTION” and “UNIT ASSEMBLY” in the process hierarchical structurearea 288 of the bills of materials definition screen 280.

[Bills of Materials Definition Screen (Process) after Designated Dateand Time is Changed]

Next, a change in the display content of the screen after registrationof the process branch due to the change of the designated date and timewill be described with reference to FIG. 27 .

FIG. 27 illustrates a change example of the display content of thescreen (bills of materials definition screen) after registering aprocess branch due to a change in designated date and time.

In the date and time designation field 289, the date and time to bedesignated is changed from “2020/01/01” to “2018/01/01”, and the displaybutton is pressed. Due to this, the hierarchical structure of processesassociated with an effective period including “2018/01/01” is displayed.For example, in FIG. 27 , a process having a three-layer hierarchicalstructure is illustrated by one path. That is, the sequence of “CABLEPRODUCTION”, “SORTING”, and “UNIT ASSEMBLY” is displayed. This is thehierarchical structure of the process before adding the branch processillustrated in FIG. 25 .

The hierarchical structure data of the processes for each effectiveperiod is stored in the nonvolatile storage 57.

[Display Example of Business Data]

Next, screen display when the business application 730 acquires datafrom the performance data management device 200 through the business ETL710 will be described.

FIG. 28 illustrates an example of screen display when the businessapplication 730 acquires data from the performance data managementdevice 200. FIG. 28 illustrates a business performance data list 721stored in the business data storage section 720 and accessed by thebusiness application 730. The business performance data list 721 is anexample of data accessed by the business application 730 according tothe purpose, and is not limited to this example.

The business performance data list 721 is created by the business ETL710 and is displayed in a table format. The business performance datalist 721 has an item name field, a process name field, a version field,an ST field, a performance start time field, and a performance end timefield.

The item name field indicates the name of the item specified by the itemID of the actual process table 611 (FIG. 12 ).

The process name field indicates the name of the process specified bythe process ID of the actual process table 611 (FIG. 12 ). The businessETL 710 acquires the names of the item name field and the process namefield from the master data 620 in the business data storage section 600.

The version field indicates the version of master data updated on theitem update screen 230 (FIG. 18 ), for example.

The ST field indicates the time in the ST field displayed on the processaddition screen 260 or the process update screen 270.

The performance start time field indicates the performance start time ofthe actual process table 611 (FIG. 12 ), the time at which the processis actually started.

The performance end time field indicates the performance end time of theactual process table 611 (FIG. 12 ), the time at which the process isactually ended.

In the first record of the business performance data list 721, the itemname is “TELEVISION A”, the process name is “painting”, the version is“1”, the ST is “120”, the performance start time is “2018/12/2809:00:00”, and the performance end time is “2018/12/31 17:00:00”. In thesecond record, the item name is “TELEVISION B”, the process name is“PAINTING”, the version is “2”, the ST is “120”, the performance starttime is “2019/01/01 09:00:00”, and the performance end time is“2019/01/03 17:00:00”.

Thus, since (the effective period of) the data read from the master data620 is different depending on the performance start time and theperformance end time, the item name changes from the television A to thetelevision B. In the present example, since the data read from themaster data 620 is different, the process name, the version, and the STare also changed.

As described above, the performance data management device 200 accordingto the first embodiment of the present invention includes: theperformance data processing section 310 that receives the performancedata 110 generated by the manufacturing site system 1; the performancedata storage section 410 that stores and accumulates the performancedata 110 received by the performance data processing section 310; themaster data storage section (business data storage section 600) thatstores the master data 620 has data to be basic information when theperformance data 110 is managed; the business data generation section500 that generates business data (performance data 610) by processingthe performance data 110 into a structure used by the businessapplication 730 based on data (data item and field) to be the basicinformation of the master data 620; and the business data storagesection 600 that stores the business data generated by the business datageneration section 500. Then, the master data 620 includes an attributethat represents start of an effective period of data to be the basicinformation (effective period start date) and an attribute thatrepresents end of an effective period (effective period start date).

In the present embodiment configured as described above, it is possibleto ensure consistency of related data by the attribute of this effectiveperiod even if the content of the performance data of the manufacturingsite system is changed.

When the business performance data list 721 is viewed through thebusiness application 730, the effective period of the data is notdisplayed. Therefore, the user can use the performance data withoutbeing conscious of the effective period of the data.

In the performance data management device 200 according to the firstembodiment of the present invention described above, the business datageneration section 500 generates business data from performance data onthe basis of the effective period of the data to be the basicinformation of the master data.

In the performance data management device 200 according to the firstembodiment of the present invention described above, the business datageneration section 500 determines whether an invalid value has been setin the performance data 110 on the basis of the effective period of thedata to be the basic information of the master data.

The performance data management device 200 according to the firstembodiment of the present invention described above includes the masterdata registration section 210 that registers the master data 620 intothe master data storage section (business data storage section 600) inaccordance with an instruction from the operation section 56. Whenregistering master data, the master data registration section 210invalidates the value instructed from the operation section 56 in a casewhere the value of the effective period instructed from the operationsection 56 is an invalid value as an effective period.

In the performance data management device 200 according to the firstembodiment of the present invention described above, when registeringthe master data, the master data registration section 210 outputs anerror in a case where the value of the effective period instructed fromthe operation section 56 is an invalid value as an effective period.

In the performance data management device 200 according to the firstembodiment of the present invention described above, when registeringthe master data, the master data registration section 210 displays, onthe display section 55, a registration screen (the item addition screen220 or the process addition screen 260) representing the hierarchicalstructure of components or processes necessary for assembly of the itemto be manufactured.

In the performance data management device 200 according to the firstembodiment of the present invention described above, the master data 620has data to be the basic information in which an effective period is setfor each component necessary for assembly of the item to bemanufactured.

In the performance data management device 200 according to the firstembodiment of the present invention described above, in a case where themaster data 120 including data to be the basic information when managingthe performance data 110 is acquired from the manufacturing site system1, the business data generation section 500 determines whether toregister the master data 120 on the basis of a state of the flag(update/delete flag 122) for registering or updating the master data 120included in the acquired master data 120 into the master data storagesection (business data storage section 600).

Second Embodiment

In general, as four elements of production, resources used in businesscan be classified into so-called 4M, i.e., man, machine, material, andmethod. Then, business is analyzed from the viewpoint of the fourelements of production in order to achieve key performance indicator(KPI) targeted by a management organization.

FIG. 29 illustrates a configuration example of performance dataclassified into four elements of production according to the secondembodiment of the present invention.

As the types of the performance data, FIG. 29 illustrates performancedata 110A where a man is a resource, performance data 110B where amachine is the resource, performance data 110C where a material is theresource, and performance data 110D where a method is the resource.

(Man)

As attributes (data items), the performance data 110A includes a 4M type131, a resource ID 132, and a contact name 133, for example, in additionto the item ID 111, the process ID 112, the product ID 113, the eventtype 115, and the event occurrence time 116.

The 4M type 131 stores information indicating the type of resource foruse in practice of business (generating performance data). In thepresent embodiment, it is indicated which element in the 4M ofproduction the performance data belongs to. This 4M type informationmakes it possible to sort the performance data for each of the 4M type.

The resource ID 132 stores a resource ID corresponding to a resourcename (in charge of painting, in charge of drying, and the like) definedby master data not illustrated. In this master data, a relationshipbetween business and resources associated with the business is defined.

The contact name 133 stores the name of the person in charge of workengaged in business as information indicating details of the resource.

(Machine)

As attributes (data items), the performance data 110B includes the 4Mtype 131, the resource ID 132, and a name 134, for example, in additionto the item ID 111, the process ID 112, the product ID 113, the eventtype 115, and the event occurrence time 116.

The resource ID 132 stores a resource ID corresponding to a resourcename (painting device, drying device, and the like) defined by masterdata not illustrated.

The name 134 stores the name of the machine used for business asinformation indicating details of the resource.

(Material)

As attributes (data items), the performance data 110C includes the 4Mtype 131, the resource ID 132, a member name 135, and a quantity 136,for example, in addition to the item ID 111, the process ID 112, and theproduct ID 113.

The resource ID 132 stores a resource ID corresponding to a resourcename (members, components, materials, and the like) defined by masterdata not illustrated.

The member name 135 stores the names of members (components), materials,and the like used or produced in business as information indicatingdetails of the resource.

As information indicating performance, the quantity 136 storesinformation indicating an increase or decrease from a set value (initialnumber, target number, or the like) of the quantity of a target member,for example. This may be a value of the quantity of a target member.

(Method)

As attributes (data items), the performance data 110D includes the 4Mtype 131, the resource ID 132, a procedure name 137, and a result 138,for example, in addition to the item ID 111, the process ID 112, and theproduct ID 113.

The resource ID 132 stores a resource ID corresponding to a resourcename (methods, procedures, and the like) defined by master data notillustrated.

The procedure name 137 stores the name of the method (procedure) used inbusiness as information indicating details of the resource.

As information indicating performance, the result 138 stores informationon a result (good, not good, or the like) of execution of a methodinstructed in business.

In the second embodiment described above, an example in whichperformance data (resource) is classified into four elements ofproduction has been described, but it may be classified into threeelements or two elements of the four elements. Alternatively,performance data (resource) may be classified into a type of elementsdifferent from the four elements of production.

The present invention is not limited to the first and second embodimentsdescribed above, and can be applied to general systems such as FAsystems and process automation (PA) systems. The present invention issuitably applied to a system in which a start time and an end time of aprocess, a work, or the like are obtained as performance data.

Furthermore, the present invention is not limited to each of theabove-described embodiments, and it goes without saying that variousother application examples and modifications can be taken withoutdeparting from the gist of the present invention described in theclaims.

For example, each of the above-described embodiments is described withthe configuration of the performance data management device in detailand specifically in order to describe the present invention in aneasy-to-understand manner, and the present invention is not necessarilylimited to those including all the constituent elements described above.A part of the configuration of an embodiment can be replaced with aconstituent element of another embodiment. A constituent element ofanother embodiment can be added to the configuration of an embodiment.Another constituent element can be added to, replaced with, or deletedfrom a part of the configuration of each embodiment.

The above-described configurations, functions, processing sections, andthe like may be partially or entirely implemented by hardware bydesigning with an integrated circuit, for example. A field programmablegate array (FPGA), an application specific integrated circuit (ASIC), orthe like may be used as the hardware.

Each constituent element of the performance data management deviceaccording to the first and second embodiments described above may beimplemented in any hardware as long as each piece of the hardware cantransmit and receive information to and from one another via a network.The processing performed by a certain processing section may beimplemented by one piece of hardware or may be implemented bydistributed processing by a plurality of pieces of hardware.

REFERENCE SIGNS LIST

-   110 performance data-   120 master data-   127 data effective period start date-   128 data effective period end date-   200 performance data management device-   210 master data registration section-   220 item addition screen-   230 item update screen-   240 bills of materials definition screen (item)-   241 BOM management information area-   248 component hierarchical structure area-   260 process addition screen-   270 process update screen-   280 bills of materials definition screen (process)-   288 process hierarchical structure area-   310 performance data processing section-   320 master data processing section-   410 performance data storage section-   420 master data storage section-   500 business data generation section-   600 business data storage section-   610 performance data-   611 actual process master table-   620 master data-   621 item master table-   622 process master table-   623 BOM master table-   624 sequence master table-   730 business application-   1000 business management system

1. A performance data management device, comprising: a performance dataprocessing section that receives performance data generated by amanufacturing site system; a performance data storage section thatstores and accumulates the performance data received by the performancedata processing section; a master data storage section that storesmaster data that has data to be basic information when the performancedata is managed; a business data generation section that generatesbusiness data by processing the performance data into a structure usedby a business application based on data to be the basic information inthe master data; and a business data storage section that stores thebusiness data generated by the business data generation section, whereinthe master data includes an attribute that represents start of aneffective period of data to be the basic information and an attributethat represents end of the effective period.
 2. The performance datamanagement device according to claim 1, wherein the business datageneration section generates the business data from the performance databased on the effective period of data to be the basic information of themaster data.
 3. The performance data management device according toclaim 2, wherein the business data generation section determines whetheran invalid value has been set in the performance data based on theeffective period of data to be the basic information of the master data.4. The performance data management device according to claim 3,comprising: a master data registration section that registers the masterdata into the master data storage section in accordance with aninstruction from an operation section, wherein when registering themaster data, the master data registration section invalidates a valueinstructed from the operation section in a case where a value of theeffective period instructed from the operation section is an invalidvalue as an effective period.
 5. The performance data management deviceaccording to claim 4, wherein when registering the master data, themaster data registration section outputs an error in a case where avalue of the effective period instructed from the operation section isan invalid value as an effective period.
 6. The performance datamanagement device according to claim 5, wherein when registering themaster data, the master data registration section displays, on a displaysection, a registration screen representing a hierarchical structure ofcomponents or processes necessary for assembly of an item to bemanufactured.
 7. The performance data management device according toclaim 1, wherein the master data includes data to be the basicinformation in which the effective period is set for each componentnecessary for assembly of an item to be manufactured.
 8. The performancedata management device according to claim 1, wherein in a case wheremaster data including data to be basic information when managing theperformance data is acquired from the manufacturing site system, thebusiness data generation section determines whether to register themaster data based on a state of a flag for registering or updating, intothe master data storage section, the master data included in the masterdata having been acquired.
 9. The performance data management deviceaccording to claim 1, wherein types of the performance data includeperformance data where a man is a resource for use in practice ofbusiness, performance data where a machine is the resource, performancedata where a material is the resource, and performance data where amethod is the resource.
 10. A business management system comprising: aperformance data management device; and a business application that usesperformance data managed by the performance data management device,wherein the performance data management device includes a performancedata processing section that receives performance data generated by amanufacturing site system, a performance data storage section thatstores and accumulates the performance data received by the performancedata processing section, a master data storage section that storesmaster data that has data to be basic information when the performancedata is managed, a business data generation section that generatesbusiness data by processing the performance data into a structure usedby the business application based on data to be the basic information inthe master data, and a business data storage section that stores thebusiness data generated by the business data generation section, and themaster data includes an attribute that represents start of an effectiveperiod of data to be the basic information and an attribute thatrepresents end of the effective period.